iCalendar Transport-Independent Interoperability Protocol (iTIP)

iCalendar Transport-Independent Interoperability Protocol (iTIP) draft-ietf-calsify-2446bis-02 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." Abstract This document specifies a protocol using the iCalendar object specification to provide scheduling interoperability between different calendar systems. This is done without reference to a specific transport protocol so as to allow multiple methods of communication between systems. Subsequent documents will define profiles of this protocol using specific interoperable methods of communications between systems. semantics for group scheduling methods commonly available in current calendar systems. These scheduling methods permit two or more calendar systems to perform transactions such as publish, schedule, reschedule, respond to scheduling requests, negotiation of changes or cancel. Change History (to be removed prior to publication as an RFC) Changes in-02: a. Tweaked abstract wording. b. Fixed some improper references. c. Removed bogus TZOFFSET entry from VTIMEZONE restriction table. d. Changed TZNAME entry in VTIMEZONE restriction table to "0+" from "0 or 1" to fall in line with 2445. e. Changed COMMENT entry in component restriction tables to "0+" from "0 or 1" to fall in line with 2445. f. Added ATTENDEE entry in VALARM restriction table to match email alarm type in 2445. g. Changed CATEGORIES entry in component restriction tables to "0+" from "0 or 1" to fall in line with 2445. h. Changed RESOURCES entry in component restriction tables to "0+" from "0 or 1" to fall in line with 2445. i. Changed CONTACT entry in VFREEBUSY restriction table to "0 or 1" from "0+" to fall in line with 2445. j. Made UID required in VFREEBUSY publish. k. Added COMPLETED entry in VTODO restriction tables to fall in line with 2445. l. Added REQUEST-STATUS entry in VJOURNAL restriction tables to fall in line …